Overview

In general, Application Editor provides a graphical environment within which you can construct your transport model.

In Application Editor you are dealing with representations of programs. A typical session involves choosing a program to be run, preparing program runs, editing data files and then running the program.

When constructing a model, you will need to run several programs, one after the other. Files produced by one program will be input to other programs. In Application Editor you arrange the data flow for such runs using the menus and the mouse. You will get immediate visual feedback on the screen of all your actions and Application Editor checks your actions to a certain degree to reduce the possibilities of making mistakes.

Application Editor does most of the work involved with keeping track of files and filenames. Application Editor can create file names automatically limiting the need to remember them. Having the computer do this work reduces the chance of using incorrect data files in your runs.

Models are often run for different scenarios, that is, the same model form but with altered data corresponding, say, to different planned transport schemes. This is best handled by the scenario management facilities in CUBE which are supported by various functions in Application Editor. Non-CUBE users need to implement scenarios by creating different versions of an application. You first create a framework of programs and files as described above. This framework contains information of all programs and files that are used in the base version of the scenario. You also specify what data (files) should vary between scenarios. You then use Application Editor to create new versions of the application in order to implement new scenarios.

Although Application Editor provides the power to let you set up large project batch runs and scenarios, you are not restricted to follow a certain pre-designed way of working. Application Editor is a set of tools and you are employing techniques using these tools. How the tools are used is up to you.

Application Editor provides a hierarchical flow chart style that offers the following:

• A clear view of the individual processes that form the complete process, the flow of data from one process to another, and the order in which the processes are run.

• A clear view of the data that is input to, and output from each process.

• A convenient means of editing and viewing that data.

• A convenient interface for running either part of the process, or the whole thing.

Application Editor is the primary interface for model development. Double-clicking certain types of files, for example a network, will read the network and display it, allowing the network to be edited. The example below shows the Cube Voyager Demonstration Model.

The application is made up of a set of numbered boxes, where each such box is either a Program box, or a Group box. A group box represents a group of programs defined in another application file. Groups are used to split up the functionality into logical sections thus making the application more readable as it prevents the need for a mass of programs to be together on one display. Groups are shown with taller boxes than the program boxes.

The numbers on the boxes reflect the order in which the boxes are run, called the execution order. In the example, there are six Group boxes, along with a Loop control.

Each program/group has a set of data boxes attached to it which define its input and output data files. Here, the Trip Distribution group has Highway Costs and Trip Ends tables as inputs, and a Person Trips matrix as an output. The output has a line coming out of it to indicate that it is passed on as an input to the Mode Choice group.

Double-clicking a group box opens the application file that represents that group. For example, double-clicking the Trip Distribution group box will show the following:

So, the Trip Distribution group consists of two Program boxes: DISTRIBUTION and MATRIX.

In both examples, the application has been annotated with text to describe the processes involved.

To edit the data used in an application, there is no need to go hunting for the data in Windows Explorer. Simply double-click the data box. This will load the data into a relevant editor. At any time, you may right-click a file box, select Locate on Disk, and Cube will highlight the file (or database) in Windows Explorer.

A program can be run by double-clicking its box. There is also a menu command to run a sub-group of the application or the whole application.

Application Editor is of value in other important respects as a:

Project-Based Tool

Application Editor is largely structured around the concept of applications, which are like “projects” so that the use of CUBE Voyager, can be strongly linked with the varied interests and features of users’ own sets of projects. Application Editor’s method of grouping a transportation model into subtasks is valuable when creating larger models. The use of subtasks also makes it easy to re-use a subtask in another model, thus creating the user’s own library of re-usable model functions.

Application Editor can be used to “sketch” out the structure of a model before it is populated with data or parameters. This allows the model structure to be discussed and refined before resources are committed to its implementation.

File Management System

Practical applications of CUBE Voyager, can use and generate many files, Application Editor automates such functions as file naming and appropriate deletion of output files. It provides techniques for handling model scenarios efficiently. The visualization of the connections between files minimizes the chance of inputting the wrong files to a program.

Automated Model Documentation System

The value of many models is lost when future users cannot understand the structure or function of a model which has been insufficiently documented in the original rush to create it. Application Editor naturally documents many aspects of models as they are developed; if its facilities are used appropriately, and in conjunction with the documenting features of the chosen package, this can produce a well-documented model with minimal effort.

Provider of Help

Application Editor supports several levels of assistance to users:

• Standardized modeling procedures, provided as Application Editor application files and fully documented, give the basis for rapid development of practical modeling applications.

For an overview of how to work and get started with Application Editor go to Build Applications .